Skip to content

Release Python SDK 2.19.0: all() member failures no longer block runs - #342

Merged
rmcdaniel merged 2 commits into
mainfrom
release/sdk-python-2.19.0
Nov 18, 2026
Merged

rmcdaniel merged 2 commits into
mainfrom
release/sdk-python-2.19.0

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Prepares the Python SDK 2.19.0 release from current main (88e3075). Not tagged or published.

What ships (since 2.18.0)

Package changes since 2.18.0 are #341, #340 and #322. They add public API and a fix with no breaking change, so this is a minor release.

This PR changes the version metadata (pyproject.toml), the CHANGELOG, and retargets the installed retry-cap qualification cell (ci.yml, activity_acceptance_release.py, published-retry-cap.json, its test and README) from 2.18.0 on Server 3.12.0 to the 2.19.0 candidate on native Server 3.13.0 (index sha256:30ccaf2c…, source 2d1244be, amd64 sha256:6cdcb909…).

Release notes: the visible effect, checked live

On native Server 3.13.0 (default config, local capped containers), with a 7-member all() whose second member fails at once, caught and compensated:

result
2.18.0 worker resends 7 commands, 409 parallel_sequence_mismatch, run stays waiting
2.19.0 source worker on a new run record_side_effect + compensation in one task (no resend)
blocked 2.18.0 run, then 2.19.0 worker only stays waiting. The Server has no workflow task for it and sends no new one
same, after a signal signal recorded, still waiting. repair refused
same, repair while a member still runs refused, development_workflow_task_repair_active_work_unqualified
same, repair after every member settled, no signal repair_dispatched. The 2.19.0 worker raised the failure, compensated, run completed

So the CHANGELOG states both effects precisely: workflow code after a group that failed early starts one sequence later, and runs blocked on 2.18.0 recover after the upgrade plus a repair once the group's members have finished. Upgrading alone does not wake them, and a blocked run that received a signal or update cannot be repaired on Server 3.13.0.

Local checks

ruff check . passes. The focused suites pass: release metadata, retry-cap cell/workflow/download, test_parallel_member_failure_open_siblings and the replay regression corpus (209 passed). On main, CI for a9d5c76 failed once, in Python 3.10 test_discard_keeps_generator_context_tokens_and_cannot_borrow_parent_time[cyclic-finalizer] (a GC-finalizer timing test). The next main run at 88e3075 passed the same cell.

Remaining release steps

  1. Build-only candidate run of this head, then review its exact wheel and sdist.
  2. Commit only .github/release-candidates/2.19.0.json on this branch.
  3. gh workflow run ci.yml --ref release/sdk-python-2.19.0 -f activity_retry_cap=true -f retry_cap_artifact_source=candidate.
  4. Merge with a merge commit at the reviewed head (--match-head-commit).
  5. Annotated tag 2.19.0 on the merge commit, then push it. That triggers publish.yml.
  6. Registry repeat: ci.yml on main with retry_cap_artifact_source=registry.

🤖 Generated with Claude Code

Release the all() member-failure fix that no longer resends an open
group (#338, #341), WorkflowContext.schedule_origin (.github#243, #340)
and typed request_id_ambiguous signal/update refusals (.github#216,
#322). Retarget the installed retry-cap qualification cell to the
2.19.0 candidate on native Server 3.13.0.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@rmcdaniel

Copy link
Copy Markdown
Member Author

Candidate review. Build-only run 44343865375 (attempt 1) built head 86effbf4. Its dist-handoff.tar artifact 14443574939 has SHA-256 7d2132af…. Reviewed offline:

  • wheel durable_workflow-2.19.0-py3-none-any.whl 1f18d038f24a6ad9440e03837e634b99a3f870afaf9c4a874829fca48737a056: 53 members. Every non-dist-info file is byte-identical to src/ at 86effbf4, the file set equals the 2.18.0 wheel's, and METADATA is Version: 2.19.0.
  • sdist durable_workflow-2.19.0.tar.gz 57aaba83102474b77283f3d7b1bb862635c846378e8c5155d228bc910b4b41a6: every tracked file is byte-identical to Git at 86effbf4, and there are no untracked members apart from generated PKG-INFO, setup.cfg and egg-info.

4e84b0d6 adds only .github/release-candidates/2.19.0.json, which records these identities. Next is the candidate retry-cap cell on Server 3.13.0.

🤖 Generated with Claude Code

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel merged commit d1c9ecd into main Nov 18, 2026
42 checks passed
@rmcdaniel

Copy link
Copy Markdown
Member Author

Published, with the post-publish qualification not green.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant